Skip to content

fix(vtable): avoid frozen row height duplication - #5255

Merged
fangsmile merged 13 commits into
developfrom
fix/issue-4904-frozen-row-gap
Aug 3, 2026
Merged

fix(vtable): avoid frozen row height duplication#5255
fangsmile merged 13 commits into
developfrom
fix/issue-4904-frozen-row-gap

Conversation

@fangsmile

Copy link
Copy Markdown
Contributor

What\n- Fix table height calculation when top frozen rows include body rows and bottom frozen rows are also configured.\n- Add a minimal debug demo for issue #4904.\n\n### Why\nWhen frozenRowCount is greater than the column header level, frozen body rows are moved into the header area, but the previous scenegraph group-height based table height calculation could count those rows again through bodyGroup.height. This produced a blank gap before the bottom frozen rows.\n\n### Verification\n- Reproduced with frozenRowCount: 5, bottomFrozenRowCount: 2, 10 records, 800x800 container.\n- Verified the gap is removed after the fix.\n- Added bugserver case: https://bugserver.cn.goofy.app/case?product=VTable&fileid=6a69f6177406d0005d72f226\n\n### Related\n- Closes #4904

@fangsmile
fangsmile merged commit 8986873 into develop Aug 3, 2026
7 of 8 checks passed
@fangsmile
fangsmile deleted the fix/issue-4904-frozen-row-gap branch August 3, 2026 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] 数据不足一屏时,设置冻结行,表格样式错乱 [Bug] 冻结行后中间出现空白行

1 participant